feat(player): respawn at a personal spawn point set by a bed - #153
Open
xRookieFight wants to merge 1 commit into
Open
feat(player): respawn at a personal spawn point set by a bed#153xRookieFight wants to merge 1 commit into
xRookieFight wants to merge 1 commit into
Conversation
xRookieFight
force-pushed
the
feat/beds
branch
from
September 3, 2026 10:38
aba2523 to
e8960ef
Compare
xRookieFight
force-pushed
the
feat/beds
branch
from
September 3, 2026 11:02
e8960ef to
108d22f
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Respawning always dropped the player at the generator's spawn column, and there was no way to change that. This adds the personal spawn point and the two ways to set one.
%tile.bed.noSleeprather than silently accepted./spawnpoint [player] [x y z]sets it explicitly, defaulting to the target's current position. The write goes through the target's own world runtime, so the console and another player's session thread both reach it the same way.Related issue
Part of #142
Deliberately not in this PR, because each depends on work tracked elsewhere:
/setworldspawn: the world spawn is still the generator's, and making it settable means making the world metadata writable at runtime.Checklist
v -check .is cleanv test server/player,server/cmd/default,server/session/combat_test.v,items_test.vare greenpub/capitalized exports, no import cycles, minimal comments)world_call/wr.submit/WorldTx), never through a global Hub actor